Software export compliance

ABSTRACT

A system and method for determining export requirements for a content file may include examining a content file to identify content used by or included in the content file that is subject to export control, determining, in response to the identified content, export requirements that are applicable to the content file, and providing an indication of the determined export requirements.

TECHNICAL FIELD

The invention generally relates to systems and methods for compliance with export regulations. More particularly, the invention relates to methods and systems for identifying content that is subject to export controls, and facilitating compliance with such export controls.

BACKGROUND

In the United States and in other countries, government controls have been placed on certain technology to prevent transfer to foreign nationals. The regulations governing such restrictions generally are complicated, at least in part because they depend on the technology in question and the nationality of potential recipients. Penalties for non-compliance may be civil and/or criminal, and so may include fines and imprisonment as well as loss of export privileges.

In the case of software, certain types of software, and software containing or using certain types of algorithms, may be subject to export controls. For example, software for use in or with military weapons may be included in a category of items that may not be exported to certain countries without government approval. Software not intended for military use still may be restricted, for example, if it includes certain types of encryption technology. This encryption technology may be publicly available, and export may be allowed, but only upon completion of required documents and/or approval.

At least in part because of the complexity of the rules, a company that has a software product or a product that contains computer software, particularly a non-military product, may have difficulty determining the export controls that are applicable to their product. The company may not even know what to look for, let alone understand the implications of the software tools and algorithms included in the company's software. This problem is compounded by the availability of encryption technology on internet web sites, such that it is possible for product developers to download and incorporate encryption technology into a company's products without knowledge or approval of management.

SUMMARY OF THE INVENTION

In general, in one aspect, the invention relates to methods and systems for identifying content that may be subject to export controls, and facilitating compliance with such requirements. In some embodiments, a method for determining export requirements for a content file may include examining a content file to identify content used by or included in the content file that is subject to export control, determining, in response to the identified content, export requirements that are applicable to the content file, and providing an indication of the determined export requirements.

The content file(s) under examination may be, for example, one or more of a software element (e.g., a source code file and/or an object code file for an application program, a library, and so on), a multimedia presentation, a video segment, an audio segment, a textual representation, a work of art, a visual representation. Regions of interest in the content file may be identified, where the regions of interest may be sections of the content files that are indicative of content that may be subject to export control. The examination may be accomplished with a tool, such as an export compliance tool, as described here.

In general, in one aspect, the invention features a method for export compliance. The method includes conducting a computer-assisted examination of one or more content files. The method includes, in response to the examination results, identifying content used by or included in the one or more content files that is indicative of content subject to export control. The method includes determining, in response to the identified content, export requirements applicable to the one or more content files. The method includes providing an indication of the determined export requirements.

The method may include receiving information about the expected use of the content file. This information may be received before or after one or more of the other steps. The determining step may include making a determination in response to the identified content and the received information regarding expected use.

The content files may be computer software files (e.g., source code and/or object code). The content subject to export control may be an encryption algorithm.

In one embodiment, the content subject to export control may be identified by presenting examination results to a user. In another embodiment, the content subject to export control may be identified without user intervention.

Various embodiments may include some or all of the following features.

The method may include identifying a first portion of the examined content file that is similar to a portion of a first comparison content file, where the comparison content file is subject to export control. The method may include identifying a second portion of an examined content file, determining whether the first portion and the second portion of the examined content file match the same comparison file. The method may include considering one or two or more of the following, alone or in combination: information about other matches with the collection associated with the comparison files, information about directory and/or file names associated with comparison files, information about date information associated with the comparison files, version control and/or content management information, build information (e.g., information based on make files, build scripts, unit tests, and so on), specific words or text strings included in a file, a critical mass of words or text strings included in a file, data values included as data, author information, structure of code, the use of certain mathematical operations, information on standards implemented, license information associated with the comparison files, an indicator that a comparison is believed to be an original, and an indicator that a comparison is not an original. Each type of information may be used separately and/or in combination with other information, mentioned here or otherwise.

Similarity may be determined by any suitable technique or techniques, alone or in combination with others. A few examples include, but are not limited to comparing tokens, comparing content, comparing data derived from content, comparing text strings, and comparing license text, comparing algorithmic operation, comparing exact strings, and comparing static data.

The portions may be portions of content in any form, such as binary, ascii, etc., and may be formatted in any manner, such as into records, or subgroups, lists, and so on. In various embodiments, there may be three, four, or more portions that match portions of comparison files. For example, the method may include identifying a third portion of the examined content file that is similar to a portion of a third comparison content file, and determining whether one of the first portion, the second portion and the third portion of the examined content file is a superset of one or more of the others, and if so, determining that the portion of the comparison file that matches the superset is a best match with the first content file. This may be extended to a fourth, fifth, sixth, and so on.

In various embodiments, a method may include aggregating the determined export requirements with export requirements applicable to other content files. In various embodiments, a method may include aggregating the determined export requirements with export requirements obtained from publicly available export information.

In general, in another aspect, the invention relates to a system for facilitating export compliance. The system includes an examination subsystem for performing an examination of one or more content files, and identification subsystem for identifying in response to examination results content used by or included in the one or more content files that is indicative of content subject to export control, a determination subsystem for determining in response to the identified content export requirements applicable to the one or more content files, and an indication subsystem for providing an indication of the determined export requirements.

In general, in another aspect, the invention relates to determining export requirements for a software program, by examining a software program, identifying a portion of the software program indicative of encryption technology included in the software program, determining export requirements associated with the encryption technology indicated by the identified portion of the software program; and providing an indication of the determined export requirements for the software program.

In general, in another aspect, the invention relates to a method for examining a software program to identify an algorithm used in the software program. The method may include identifying a first portion of the software program that is similar to a portion of a comparison software program. The method may include determining that the first portion is associated with an algorithm. The method may include providing an indication that the software program uses the determined algorithm. There may be one, two, or more different algorithms used, and two or more algorithms may be used in combination.

In various embodiments, the algorithm may be subject to export controls. The method may further include analysis of the algorithm, or data used by the algorithm, to determine characteristics of the implementation of the algorithm. For example, the method may include analysis of the algorithm to determine the key length of key data employed by the algorithm.

In general, in one aspect, the invention relates to an export compliance tool that is used in combination with a content management tool. The content management tool may be used, for example, to provide license compliance information to a user. The export compliance tool may be used as described here to provide export compliance information. In one embodiment, the examination of files described here takes place as part of a compliance effort that includes both license compliance and export compliance. Information, reports, and documentation are provided that include both license compliance information and export compliance information. It should be understood that there may be efficiency benefits of such a tool, in that the examination of content may only need to be performed once, with results that are applicable to both license compliance and export compliance.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, aspects, features, and advantages of the invention will become more apparent and may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a flowchart of an embodiment of a method.

FIG. 2 is a block diagram of an embodiment of an export compliance system.

FIG. 3-FIG. 19 depict screen displays for an exemplary embodiment of an export compliance system.

FIG. 20 is a flowchart of an embodiment of a method.

DESCRIPTION

Referring to FIG. 1, a method 10 for providing export requirements includes examining one or more content files for indications that the content files uses or contains content that is subject to export control (STEP 11). A content file may be a traditional element of data storage in a file system, or any other suitable data store or unit of storage, including without limitation one or more files. A content file may be examined in any useful way, using any suitable technique. For example, information in the content file may be examined, or information derived from the content file may be examined. Some techniques for examining a content file are described below, and others may be applied as well. Some techniques involve comparing the file or portions of the file to portions of comparison files that are or may be subjection to export control. Some techniques involve string comparison, data comparison, interface analysis, and so on. Some techniques may require examination of only one content file at a time, and others may involve examination of a number of related files.

A file may be examined for indications of content that is subject to export control. For example, one indication of that content files are subject to export control is if a content file appears to be whole or partial copies of a comparison file that is known to be subject to export control. Another indication that a content file is subject to export control is if the file contains access information or interface information that is associated with a content file that is subject to export control. Another indication that a content file is subject to export control is that it contains text strings associated with content that is subject to export control. Another indication is that the content includes, links to, or otherwise makes use of a content file that is subject to export control.

The user and/or system may identify characteristics of how the content files will be used. As a few non-limiting examples: what encryption mode is used (e.g., how is the algorithm operated, the size of the key space, and so on), whether or not it is used solely for authentication, in what media encrypted data is stored, if any (e.g., in dynamic memory, static memory, hard drive, for transmission over a network), and whether the encryption is used solely for decryption to enable copy protection.

In some embodiments, the examination includes examining for indications of algorithms or interfaces or calls to algorithms of a particular type. For example, the examination may seek to identify indications that cryptographic algorithms are used. A content file may be examined, for example for known interface calls and/or semantics, similarity in computer code or comments, character strings, static data (e.g., constants), subroutines calls, and/or operational steps performed; that are indicative of cryptographic technology.

The content may be identified as content that is or may be subject to export control (STEP 12). This may be accomplished by analysis of the examination results, by further inspection or examination of the content, or by any other suitable technique. This identification may be performed manually by a user, by a user with help from the system, and/or automatically by the system. For example, the system may identify content files that match comparison files, and a user may review the matches to see whether the matches do in fact indicate a match and/or content that is subject to export controls.

Export requirements for the content file may be determined (STEP 13). This may be accomplished through analysis of the identified content. In some embodiments, this may also require additional information about the content, for example how or to whom it may be transferred. Such information may be obtained by default, using information that is already been received from a user, from other information databases, or otherwise. In some cases, additional information about the content may be requested and/or received from a user before, during, or after the steps described here.

Determination logic may be employed using information about the export requirements that are applicable to the jurisdiction in question, and information about the content in question. For example, once a user and/or system has identified that content includes and/or uses certain encryption algorithms, the system may determine the export requirements for that software, based on the identified algorithms and/or other information about the software, such as its intended use, to whom and where it will be distributed, whether it is a mass market product, whether development is or will be outsourced, whether it is an open source project, whether it is a project under test (e.g., a beta test), and so on.

In general, the determination logic will include a representation of the applicable export requirements, so that it is possible through identifying the characteristics of the content files and their use, to determine the applicable requirements. For example, a tree structure may be employed, so that the various possible conditions on the type of algorithms and their intended use will result in the determination of the applicable requirements. As another example, a lookup table may be used to make a determination. In one such embodiment, a lookup table that includes the type of distribution, the product type, the key length of the algorithm, whether it is a mass market product, whether an export classification (e.g., an ECCN) is applicable, and whether it is a restricted item are all inputs into a table that has as its result the applicable export requirements. Other table data may be used in addition or instead in particular implementations.

An indication of the export requirements may be provided (STEP 14). This indication may be a report that indicates the content identified, and the requirements that may be applicable to that content in certain circumstances. This indication may be a report of the particular requirements associated with the content based on the information about the content (e.g., to whom or where it will be distributed or transferred) that has been received.

In some embodiments, the indication may be provided in the form of a completed or partially completed document, such as an export license application, notice, or reporting form. This is intended to facilitate completion and submission of appropriate documentation for export compliance. In one embodiment, the indication may include notice in the form of an electronic mail message to be sent to a government agency for compliance with export requirements. In some embodiments, the indication may be provided to a reporting system, such as provided by a third-party vendor and/or a government. For example, the indication may be provided to the Simplified Network Application Process (SNAP) provided by the U.S. Bureau of Industry and Security (BIS) and/or to their System for Tracking Export License Applications (STELA). The information may be provided as a completed, or partially completed web page form, which may be reviewed and communicated to the relevant government agency.

In various embodiments, aggregated export requirements for multiple files, system components, hardware components, and so on may be identified and tracked. For example, by performing the above steps for each of a number of individual components, export requirements for each of the components may be identified. It would be possible to specify an aggregation of multiple components, and so aggregate the requirements for a computer program or computer system that included all of those components. In another example, if certain software components previously were identified, whether in the export compliance system, a content management system, or otherwise, the information for such files, components, or devices may be combined or aggregated. The information may have been already provided by a user, or may be obtainable by some other means, such as an outside service, web service, or otherwise. For example, if a product to be exported includes a hardware router, and there is publicly available export information associated with that router, the publicly available information may be identified and aggregated with the other information described here.

In one such embodiment, the method includes automatically accessing a publicly available database for export information applicable to a portion of a product. Another portion of the product also include export requirements determined as described here. Export information for the combined product is determined using the information from the publicly available database and the previously determined export requirements. An analogous method uses other previously determined export requirements to provide an indication of export requirements for a combined product.

In some embodiments, the functionality described here may be integrated with a licensing management system or content management system that is already tracking source code components and modules. Export compliance information may be associated with one file, multiple files, a collection of files, components, and so on, and tracked in addition to other information. Information from such a system may be applied to code files or collections of files, libraries, and so on that are identified in such a licensing management or content management system. In some such embodiments, a content management system, such as the PROTEXIP available from Black Duck Software, Inc., of Waltham, Mass., is used to track content management and licensing information as well as export requirements associated with a content file or a collection of content files. Such information may be used in the aggregated determination.

Referring to FIG. 2, in general, in one embodiment, an export compliance system may include software running on a general-purpose computer (e.g., a PC with an INTEL processor or an APPLE MACINTOSH) capable of running such operating systems as the MICROSOFT WINDOWS family of operating systems from Microsoft Corporation of Redmond, Wash., the MACINTOSH OS X operating system from Apple Computer of Cupertino, Calif., and various varieties of Unix, such as SUN SOLARIS from SUN MICROSYSTEMS, and GNU/Linux from RED HAT, INC. of Durham, N.C. (and others). The system 20 could also be implemented on such hardware as a smart or dumb terminal, network computer, wireless device, wireless telephone, information appliance, workstation, minicomputer, mainframe computer, or other computing device that is operated as a general purpose computer or a special purpose hardware device used solely for serving as a export compliance system 20.

The export compliance system 20 includes or has access to examined content 25, which may be any sort of content. The export compliance system 20 also includes or has access to comparison content 30. The comparison content 30 may be accessed directly, or may be processed in or stored in the form of comparison data 35. Such comparison data 35 may include a database or other collection of information that describes, or is generated from or derived from the content. The comparison data 35 may be used to quickly identify matches. The comparison data 35 also may include one or some combination of comparison words and strings, directory and/or file name, date, and size information, version control and/or content management information, build information, data values, author information, standards information, code structure information, mathematical operations used, license information, and so on.

The export compliance system 20 includes an examination subsystem 40. The examination subsystem examines a content file to identify content subject to export control. The examination subsystem, for example, may calculate data that is derived from the examined content, for comparison with the comparison content 30 and/or the comparison data 35. For example, the examination subsystem may produce data that may be compared with comparison files. The examination subsystem also may search for comparison data 35, e.g., particular strings or data that are not associated with a particular comparison file 30, but which are indicative of export control requirements. The examination system also or instead may identify one, two, or more other types of information, e.g., one or some combination of comparison words and strings, directory and/or file name, date, and size information, version control and/or content management information, build information, data values, author information, standards information, code structure information, mathematical operations used, license information, and so on.

The examination subsystem 40 may also determine whether there is a number of one or more of these that is above a threshold. For example, if the threshold is twenty, the examination subsystem may determine that twenty relevant words and text strings are present. If that is combined with author information, it may be used for identification.

The export compliance system 20 includes an identification subsystem 45 for identifying portions of examined content files 25 that are similar to comparison files 30. The identification subsystem 45 may use data that is generated by the examination subsystem 40 to compare the examined content files with the comparison files. In one embodiment, the identification subsystem 45 uses data calculated using content from the examined content 25 and compares it to comparison data 35, which has been calculated in a similar way, and indexed for fast retrieval. In one such embodiment, after a first identification using calculated comparison data 35, the identification subsystem 45 performs a comparison using the actual content, to identify specifically any overlap.

In one embodiment, the identification subsystem 45 may identify a first portion of an examined content file that is similar to a portion of a first comparison content file and a second portion of the examined content file that is similar to a portion of a second comparison content file. There may be other portions of other files that are also identified. The identification subsystem 45 may facilitate or assist a user in directing the identification. For example, the identification subsystem may allow a user to view examined files, and compare them to matching comparison files. The identification subsystem 45 may facilitate or assist a user in directing the identification of a particular algorithm.

For example, in one embodiment, the examination subsystem may identify a number of content files that match with content files that include or use encryption algorithms. The identification presents this information to a user, and allows the user to compare the files. The identification subsystem enables the user to indicate the algorithms that are in use in or by the examined content files. Upon completion, the system has identified the content that is subject to export control.

In some embodiments, the export compliance system 20 includes a facility for allowing a user to manually identify a component that is included. In this way, even if it is not recognized by the system, the component may be included in the analysis. In some embodiments, the export compliance system includes a facility for importing export requirements from another export system or from publicly available data relevant to all or a portion of a component.

The export compliance system 20 also may include a determination subsystem 50 for determining export requirements that are applicable to the content file. This can be accomplished in any suitable manner. For example, the determination subsystem may apply rules based on the identified content. The determination subsystem may also take into account additional information that may be provided (not shown) about the intended use of the content and/or the intended destination of the content and/or any other relevant information.

The export compliance system 20 also may include an indication subsystem 55 for providing an indication of the determined export requirements. As mentioned, this indication may take the form of a display, report, email and/or other message, warning signal, and so on, and may in some embodiments include documentation or references to documents that describe the application export requirements and/or completed or partially completed documents for submission to a government body or other agency.

Optionally, the export compliance system 20 also may include a receiving subsystem (not shown) for receiving information about the content files. This information may include the intended use for the content files, as well as other relevant information about the content files. The determination subsystem 50 may include information from the receiving subsystem in making a determination about export requirements that are applicable to a content file.

It should be understood that each of these subsystems may be implement by software modules, special-purpose hardware, or any other suitable fashion, and, if software, that they all may be implemented on the same computer, or can be distributed individually or in groups among different computers. There may be multiple instances of some or each of the subsystems, and they may be operated in any suitable manner.

There are many different techniques that can be used to identify similarities between content files. Some of these techniques include comparing the tokens in, the structure of, the flow of execution of, the copyright notices in, the license information in, the license text in, the text strings or larger sections of text in, and/or the symbol tables in the examined file or a sub-portion thereof to those in or of one or more other content files (referred to as comparison files) or sub-portions thereof. Some of these techniques may include comparing interface calls and/or semantics, interfaces implemented, use of particular character strings, static data (e.g., constants), subroutines calls, and/or operational steps. Also or instead other information may be used, such as one or some combination of comparison words and strings, directory and/or file name, date, and size information, version control and/or content management information, build information, data values, author information, standards information, code structure information, mathematical operations used, license information, and so on.

In one embodiment, the export compliance system has a large number of comparison files 30 that are of known origin. Those comparison files can be used for comparison with the examined files 25, to see whether there are any portions of the examined files that are similar to any portions of the comparison files. The comparison files may be, for example, publicly available files, files within a company's own possession, or files provided by a third party for comparison. The comparisons may be accomplished by using the files themselves, or by using data calculated from the files.

Generally, a region of interest in an examined file may be identified by its location and size within the examined file. The region may be determined to match (e.g., within a predetermined threshold of similarity) a comparison file region that also has a location and size. It may be useful, in the context of such a export compliance system, to provide a user of the export compliance system with an indication about which portion of an examined file is similar to a comparison file. Such an indication may include specification of the location and size of the matching portions of the examined and comparison file. Such an indication may include information about the comparison file, such as export restrictions, license information, code structure, mathematical operations used, authorship information, and characteristics of the technology that are relevant to export control. The indication may also include any other useful information about the comparison file. To give some examples: the project of origin, a web site or other contact information for the project authors or owners, support suppliers, royalty or other payments required for use, alternatives to the comparison files that are known to be available, test results, project usefulness ratings, security problems and/or vulnerabilities, later available versions, available modifications, and so on.

It may be possible, however, for a region of interest in an examined content file to be similar to a portion of a first comparison file, and also similar to one or more portions of other comparison files.

In the circumstance that a portion of an examined file is similar to portions of multiple comparison files, it may be helpful to provide the user with an indication of all the portions of all the files that are similar. In some circumstances, however, it is more helpful to identify the best match or matches, rather than all of the files that have similar portions. For example, if the comparison files include multiple versions of the same file, the user may be interested in only the version that is the best match. As another example, if there are multiple copies of the same file, the user may only need to see an indication of one of the copies. Likewise, if there is other information available in addition to the determination of similarity, and that information suggests that one of the comparison files is more likely to be the source of the identified content than the other comparison files, or that it is the best match, then it can be beneficial to provide only an indication of the comparison file that is the best match. This simplifies the communication to the end user, and reduces effort to be undertaken by a person in confirming the match. Techniques for determining the best match may be found in U.S. patent application Ser. No. 11/429,928, entitled “Methods and Systems for Reporting Regions of Interest in Content Files,” filed on May 8, 2006, incorporated herein by reference.

A number of techniques are described that will aid a export compliance system in identifying a region of interest in a comparison file that is the best match with a region in an examined file. These techniques may be use separately or in combination, to identify a representative region, file, or collection of files. In general, the techniques are described by way of simplified example, and should be understood to have a wide range of applicability.

In some implementations, an export compliance tool as described here is used in combination with a content management tool such as that as described in the patent application just mentioned, U.S. patent application Ser. No. 11/429,928. The content management tool may be used, for example, to provide license compliance information and the export compliance tool may be used to provide export compliance information. In one embodiment, the examination of files described here takes place as part of an effort that includes both license compliance and export compliance. Information, reports, and documentation are provided that include both license compliance information and export compliance information. It should be understood that there may be efficiency benefits of such a tool, in that the examination of content may only need to be performed once, with results provided that are applicable to both license compliance and export compliance.

FIG. 3-FIG. 15 demonstrate the operation of an embodiment of an export compliance system. It should be understood that this is one exemplary, non-limiting implementation, and that a variety of other implementations are possible.

Referring to FIG. 3, in one embodiment, a user of an export compliance tool creates a new project. Details about the project may be provided, such as the project name (called “Patent Demo” in this example) 301. The location of the files for this project, and/or other information about the project, would typically have already be configured. Further details about the project may be provided. In general, information that may be used to categorize the project with respect to the applicable export requirements will be helpful. For example, information requested may include what type of product it is 303 (e.g., for sale, use internally within an enterprise), and the intended distribution 305 (e.g., to whom and/or to where the project will be sold or distributed). Just as some examples, choices of where the product may be distributed include but may not be limited to United States only; Canada; European Union; members of a group of countries referred to as the Supp. 3 License Free Zone (LFZ); foreign subsidiaries of U.S. companies not in embargoed countries; non embargoed foreign national employees of U.S. companies; customers already covered by export licenses; private organizations in the Non License-Free Zone but not embargoed countries; government end-users in non License Free Zone countries but not embargoed countries; and embargoed countries, (e.g., E1 countries). Other information about the project may include whether the product will be sold on the mass market 307, whether the product will be worked on by an outsourcing firm 309, whether the project will be released as open source 311, whether it is a beta test release 313, and whether the product will only be used for development of other new products 315. Other information also may be used instead or in combination with any of the above, as applicable.

In general, this information, along with the specifics of the technology in question may be used to determine export requirements that are applicable to the content file. For example, with respect to encryption technology, the above information along with information about the type of encryption and the key length of the algorithm may be used to determine the applicable export requirements.

Here, the key length is used to mean the range of possible values of an encryption and/or decryption key. The key length is typically measured in bits, such that an algorithm that has a “10 bit” key length has a key that may be selected from 2¹⁰ different values. The key length of a symmetric encryption algorithm may be, for example, less than 56 bits, more than 56 bits but less than 64 bits, or more than 64 bits, with possibly different export requirements for each. Likewise, the key length of an elliptic key algorithm may be less than 112 bits, or more than 112 bits. The key length of an asymmetric key algorithm may be less than 512 bits or more than 512 bits. See, for example, B. Schneier, “Applied Cryptography” 2^(nd) ed. (1996), for example at pages 151-168, in which he describes the complexity of a brute force attack based on the key length for different types of algorithms.

Additional information about the encryption algorithm that may be useful may include whether it was modified, adapted or configured for military application, (e.g.: NSA Type 1 Suite A), or the type of cryptographic algorithm (e.g., message authentication code (MAC), cryptographic hash, digital signature, public key encryption, block cipher mode, padding system, and so on).

Referring to FIG. 4, an interface is provided to allow a user to begin content examination. A button 401 is provided to start file examination. Optionally, advanced options 403 may be enabled. For example, as an advanced option, it may be possible to configure the system to re-examine files that have not changed, or not to re-examine files that have not changed and that have already been examined. Clicking on the button 401, begins examination of the files.

Referring to FIG. 5, after examination of the files, a list of files 501 is shown. The list includes the file name, and the number of matches. The user can compare the matches to comparison files. The user can identify the algorithm based on the information provided. Thus, in this embodiment, a user is provided with matches to content that is subject to export controls, and the user is able to review the code, and make the determination about whether the content in fact matches the comparison content. In this example, the content with matches includes 4 source code files: “blowfish.c,” “sha1.c,” “sha256.c,” and “tiger.c.” Each of these files may be compared to the comparison files, to determine whether the indication of export control is correct.

Referring to FIG. 6, an exemplary file comparison is shown with the examined file 603 and a comparison file 605. The examined file is called blowfish.c in the project “Patent Demo.” In this example, the comparison file is called bfpi.h, and is said to come from the cryptlib implementation of the Blowfish encryption algorithm with a user configurable key. The file similarity is shown in the display. In this example, the match that is shown are static data, e.g., constants, that are used by the Blowfish algorithm. Scrolling the scrollbar may reveal other matches between these files. The Blowfish algorithm is subject to export controls in some cases, and so the match from the content files to this comparison file is indicative of export control. As shown in the figure, other tabs indicate other matches with comparison files.

Referring to FIG. 7, having reviewed the comparison between the examined file and the comparison file(s), the user is asked to identify the match. The user may indicate that the file does not implement or call an encryption algorithm 701. In other words, after review, the user may determine that the match was a false hit. The user may identify that the code does match with a comparison file and so the file contains content that may be subject to export control. The user may identify an encryption algorithm that is included or used by the code. As shown, the user has indicated that the examined code is from the Crypt implementation of Blowfish, and the user has determined that the key length is less than 56 bits. As the matching file indicated that the code may implement varying key length, the user may need to make the determination of the key length by examining the code. Other options may include an indication that the code actually matches another encryption algorithm in the library 705 or that the code is from a custom algorithm implementation 707, which may be specified. Additional comments also may be provided 709 to describe the match.

In this embodiment, the system identifies matches to comparison files, and user then reviews the matches and identifies the algorithm that has been found. In practice, it may make sense for an engineer to perform the analysis and identification of encryption technology, under the supervision of a compliance officer and/or attorney.

Referring to FIG. 8, in one embodiment, a user is also provided with a list of results 801 of “string searches”—searches for particular text that may be indicative of content subject to encryption control. For example, when searching for encryption technology, the compliance system may look for words like “encrypt” and “encryption” and also for the names of particular algorithms, like “Blowfish” and “MD5.” The compliance system may also search for constants that are associated with a particular algorithm. For example, some cryptographic algorithms make use of constants that are used in calculations (e.g., S-boxes). The values associated with these constants will be stored as static data in implementations of those algorithms. As shown, the list is grouped into categories of the types of searches, such as “Cipher-based words” and words associated with the “RSA Algorithm.”

Referring to FIG. 9, as an example, the search results for “Open SSL RSA functions 1” are shown. Two files contain words that are associated with this category. A user then has the opportunity to review the string matches within a file (as shown in FIG. 10), and to identify the matches once they have been reviewed.

Referring to FIG. 10, the matches for the file crypt.h are shown. Referring to FIG. 11, the user can identify the encryption technology that is associated with the hits.

It should be understood that having both string searches and comparison files may each be useful, and that the result data may be presented in combination, and in other ways. The separate display of results from comparison file searches and string searches is useful, in that it helps the user understand why content files have been selected, but the results may be presented and/or combined in a variety of ways.

Referring to FIG. 12, the user is given an opportunity to provide and/or verify additional information about the project that may determine the export requirements that are applicable. Various export regimes may include exceptions, for example, that may be applicable, such as in the United States, exceptions that apply to smart cards, short range wireless routers, banking and financial systems, open source software, and others. The user here may be asked to specify information that would be indicative of an exemption or otherwise determinative of a requirement. For example, the user may indicate that the product is self-classified according to a particular rule (e.g, in the U.S., exporters may self-classify as 5×992), or as another example, the user may indicate that the project includes an open cryptographic interface 1203. The user also may confirm the information provided in the screen of FIG. 3, such as the type of project 1205, the intended distribution 1207, whether the project is outsourced 1209, whether the project will be released as open source 1211, whether the current distribution is only for beta testing 1213, or whether it is used only for internal development of other new products 1215.

In some embodiments, the information provided is context dependent, such that the information requested is particular to other information that was provided, such as the algorithm identified, the destination specified, and so on. In this way, the system can resolve ambiguity in certain circumstances, but not burden the user with unnecessary questions.

Referring to FIG. 13, the user is presented with an indication of the determined export requirements. For example, export restrictions 1301 are shown, listing export restricted individuals, organizations, and countries. An explanation of why these requirements are applicable is also provided. The list of encryption algorithms identified 1303 that were the basis for the export requirement indication also is provided.

Referring to FIG. 14, if a notification, application, or other document is required, the export compliance system may provide a place for a user to provide information necessary or desirable for completion of the document. As shown, the system has requested that the user complete parts of a BIS notification that have not been automatically generated from the information available to the system. In this example, there is an opportunity for a user to provide description of proprietary algorithms used, pre-processing methods, post-processing methods, other communications and encryption protocols used, and encryption interfaces (e.g., API's). This information may be used to complete a notification.

Referring to FIG. 15, a draft notification is shown. The notification may be a draft paper document that can be printed and sent by mail, electronically (e.g., by electronic mail or web page) or by any other suitable means to an applicable government agency. The notification may be available for viewing and review, and if it is acceptable, the user can direct the system to print or send 1501 the notification. In some embodiments, just the information may be provided, with or without instructions for completing the required information. In some embodiments, a draft word processing document or spreadsheet may be generated. In some embodiments, text to be copied into a word processing document or other form may be provided.

Referring to FIG. 16, in one embodiment, an audit trail of certain user interaction with the system is stored that allows the same or a different user to understand the work that took place with respect to particular content files. For example, the system will allow a user to determine what code matches were identified by the system, what identifications were made by a user (with information about which user, and when the identifications were made), and a summary of the resulting analysis. This allows an administrator or other user, for example, to determine what matches were identified, whether matches were analyzed, and what conclusions were reached. This information may be useful in reconstructing previous work, or in working with an export authority.

Referring to FIG. 17, a summary of the encryption algorithm identified is provided, along with information about the content files that matched. Again, this allows an administrator or other user to review the work done with the system. As shown in the figure, the algorithm that was identified as the Blowfish algorithm matched with a number of implementations of Blowfish in a variety of software components. The identification of Blowfish and the matches would seem to be consistent. By providing this view of the analysis, it becomes easier for someone to review the work done with the system.

Referring to FIG. 18, a history report allows a user to view a work report for a particular date/time. As shown in the figure, the current work report is available, as well as a work report for Sep. 28, 2006 at 10:29 am (2006.09.28 102902). A user may select the desired date/time for report viewing.

Referring to FIG. 19, a historical work report, such as that shown in FIG. 16, is available for the past date/time selected, in this case Sep. 28, 2006 at 10:29 am. In this way, an administrator or user may determine when decisions were made, who made them, and what information they considered (e.g., what matches, etc.)

Techniques for Identifying Similarity Between Content Files

Any suitable technique that is helpful in identifying a region of similarity between an examined file and a comparison file may be used by the export compliance tool. Various embodiments of the techniques are described below. It should be understood, however, that the features of the various techniques described below are not mutually exclusive; they can exist in various combinations and permutations, even if such combinations or permutations are not made express herein, without departing from the spirit and scope of the invention. For example, the export compliance tool may employ one of the techniques described below, or two or more of the techniques described below, for example in combination. It will be understood by one of ordinary skill in the art that some of the techniques described below may be performed by the export compliance tool itself or by the export compliance tool in combination with a database server, even if it is not expressly stated as such. Moreover, it will be understood by one of ordinary skill in the art that the various described manners of inspecting the examined file may similarly be employed to inspect the one or more comparison files prior to comparing the examined file to the comparison file. Alternatively, rather than also inspecting the one or more comparison files in the manner described for the examined file, once the examined file is inspected and the relevant data or information extracted therefrom, the one or more comparison files may be searched for such specific data or information to identify matches between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, the export compliance tool inspects tokens in the examined file. Where the examined file is computer code, the export compliance tool may inspect tokens derived from the source code or from the object code of the computer code. The tokens can take a variety of forms. For example, in one implementation, the export compliance tool breaks the source code or object code down into discrete subsets of code and then, for each discrete subset of code, evaluates a hash function to generate a hash value. Optionally, the generated hash values, or a subset thereof, may then be transmitted to a database server. Either the export compliance tool or the database server, if involved, may then compare the hash values against a collection of known, or recently evaluated, hash values for discrete subsets of code within the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In another exemplary implementation using tokens, the export compliance tool generates a token for each word, or symbol, in the computer code. Each word or symbol has an assigned token. The code is thus translated to tokens, which tokens are then compared, for example individually, summarily (i.e., some but not all), or in proximate groups, to the comparison files, which may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In another exemplary implementation, the export compliance tool generates a token for each item in the code, in a manner similar to tokens generated by a compiler. For example, each token may include a pair of integers, where the first integer is the class of token representing a code element (e.g., START, END, FUNCTION CALL, SYMBOL, CONSTANT, LITERAL, OPERATION, etc.) and the second integer identifies the member of the class (e.g., for class OPERATION, members can include without limitation ADD, SUBTRACT, COMPARE; and for class SYMBOL, the token member might be the string name of the symbol, or an identifier assigned to the string name). The tokens that are generated may then be compared to tokens for the comparison files, for example individually or in adjacent or nearby token groups, which may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files. In some embodiments, for some symbol classes, only the token class types are compared. For example, for CONSTANTS and LITERALS, it may be enough to know that a CONSTANT occupied a location between an OPERATION/ADD token and an OPERATION/MULTIPLY token. The combination of some token members, in proximity to some token classes, for example, may be indicative of a match between one or more regions within the examined file and one or more regions within one or more of the comparison files. Use of this technique enables the export compliance tool to identify code that is functionally equivalent, but has been subject to non-functional, textual changes such as a global search and replace of variable names.

As another example, for Java code, the code for each of the examined file and the comparison files may be compiled into bytecode tokens, and the compiled bytecode tokens compared. Although the compiled output may be compiler specific, if the same Java compiler is used to generate the tokens that are used for comparison, any anomalies due to compiler differences can be minimized. As in the example above, if desired, steps can be taken to minimize the impact of any non-functional, textual differences, such that the comparison focuses on functional similarity as represented in a group of adjacent or nearby tokens.

In one embodiment, the export compliance tool inspects the structure of the examined file. For example, where the examined file is a source code file or an object code file, the export compliance tool may inspect the code, or subsets thereof, and generate representations of how the code is structured (e.g., representations of what certain routines, sub-routines, functions, loops, etc. use as parameters, variables, constants, etc.). The generated representations may then be compared against a collection of known, or recently generated, source code or object code structure representations for the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, the export compliance tool inspects the flow of execution of the examined file. For example, where the examined file is a source code file or an object code file, the export compliance tool may inspect the code, or subsets thereof, and generate representations of the order in which discrete sections of the code (e.g., routines, sub-routines, functions, loops, etc.) are found and/or will be executed. The generated representations may then compared against a collection of known, or recently generated, source code or object code flow of execution representations for the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, the export compliance tool inspects copyright notices in the examined file. For example, where the examined file is a source code file or an object code file, the export compliance tool may inspect the file and reproduce all copyright notices identified therein. The export compliance tool may identify such copyright notices by, for example, searching the file in a non-case-sensitive manner for the text string “copyright,” searching the file in a non-case-sensitive manner for the text string “all rights reserved,” searching the file in a non-case-sensitive manner for the text string “(c),” or searching the file for the symbol “©.” The reproduced copyright notices may then be compared against a collection of known, or recently generated, copyright notices for the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files. Also, after having identified the copyright notices within the examined file, the export compliance tool may be configured to search the comparison files for those specifically identified copyright notices. Such a search may also yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In various embodiments, the export compliance tool identifies zero, one, two, or more of: information about other matches with the collection associated with the comparison files, information about directory and/or file names associated with comparison files, information about date information associated with the comparison files, version control and/or content management information, build information (e.g., information based on make files, build scripts, unit tests, and so on), specific words or text strings included in a file, a critical mass of words or text strings included in a file, data values included as data, author information, information on standards implemented, code structure information, mathematical operations used, license information associated with the comparison files, an indicator that a comparison is believed to be an original, and an indicator that a comparison is not an original. Each type of information may be used separately and/or in combination with other information.

In one embodiment, the export compliance tool inspects license information, which may be incomplete, in the examined file. For example, where the examined file is a source code file or an object code file, the export compliance tool may inspect the file to identify all instances where license information appears. The export compliance tool may then reproduce certain license information from the identified instances, such as, for example, identifications of the licenses themselves and/or the types of the licenses, the scopes of the licenses, the durations of the licenses, the payments to be made under the licenses, or combinations thereof. The reproduced license information may then be compared against a collection of known, or recently reproduced, license information from the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, the export compliance tool inspects license text, which may be incomplete, in the examined file. For example, where the examined file is a source code file or an object code file, the export compliance tool may inspect the file to identify all instances where license text appears. The export compliance tool may then reproduce all or certain portions of the license text from the identified instances. The reproduced license text may then be compared against a collection of known, or recently reproduced, license text from the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, the export compliance tool inspects the examined file for specific text strings. For example, where the examined file is a source code file, the export compliance tool may inspect the file to identify the presence or absence of certain text strings, such as, for example, “blowfish,” “public key,” and “encryption.” Where the examined file is an object code file, the export compliance tool may employ a hexadecimal translator to inspect the file and identify the presence or absence of certain text strings in constants. Having identified certain specific text strings, the export compliance tool may then reproduce the text strings and compare them against a collection of known, or recently reproduced, text strings for the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, the export compliance tool filters its identification of specific text strings in the examined file and may also filter its comparison of the identified text strings against the comparison files. For example, where the examined file is a source code file, the export compliance tool may filter or restrict its identification of specific text strings to those which occur only in the comments or, alternatively, to those which occur only in the code. Moreover, the export compliance tool may filter or restrict its identification of specific text strings to those text strings that occur only in string constants or to those that occur only in the lowercase, and may treat all white-spaces, no matter how long, as equal. The query against the collection of known, or recently reproduced, text strings for the comparison files may also be filtered as such.

In one embodiment, rather than inspecting the examined file for specific text strings, the export compliance tool reproduces larger sections of text from the examined file, for example from the source code of the examined file, and compares those text sections against a collection of known, or recently reproduced, text sections from the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

In one embodiment, where the examined file is an object code file, the export compliance tool inspects the object code file to identify its symbol tables. Having identified the object code file's symbol tables, the export compliance tool may then reproduce the symbol tables themselves, or, alternatively, only its symbols, and compare them against a collection of known, or recently reproduced, symbol tables or symbols of the comparison files. The comparisons may yield a match between one or more regions within the examined file and one or more regions within one or more of the comparison files.

Data Matching

In one embodiment, the export compliance tool searches for particular data values that may be specific to an algorithm. To match data values in source code, for example, using a single canonical representation of the data value, the system may consider the different ways a programmer might write those values. Those ways may include different formats (e.g., decimal, hexidecimal, octal or other formats); different array types (e.g., arrays of bytes (8 bits), shorts (16 bits), words (32 bits), double words (64 bits)); different number of items per line (e.g., 1-32, depending upon what array type is used); different machine-dependent value ordering (e.g., big-endian or little-endian); different programming language array syntax (e.g., separate values by comma (as in Java, C, perl), whitespace (as in lisp, scheme)); different programming languages format specifiers (e.g., 0x (hexadecimal in Java, Perl, C), 0 prefix (octal in java, Perl, C), Z′ . . . ′, Z . . . , Z″ . . . ″ (hexadecimal in Fortran), 0′ . . . ′, O . . . , O″ . . . ″ (Octal in Fortran), B′ . . . ′, B . . . , B″ . . . ″ (binary in Fortran), $ (hexadecimal in Pascal), 2# . . . , 8# . . . , 16# . . . (binary, octal, and hexidecimal in Pascal), 16# . . . # (hexadecimal in Ada and VHDL) and so on); different programming languages type specifiers (e.g., ul, ull appended in C); abbreviated and extended forms (e.g., leading zeros (e.g., 0x000A or 0xA)); and variations and combinations of the above. In some embodiments, comparison files are generated that have the variations of the desired values, which are then used for comparison. In other embodiments, a separate search and/or examination is made for the particular values, as part of a text string search or otherwise.

To match data in object files, the system may need to consider some of the above, such as value-ordering (e.g., big-endian or little-endian) and array types, as well as different binary formats (e.g., JAVA bytecode, a.out, ELF, PE, COFF, EXE, COM, XCOFF, and PEF binary formats, .NET “Managed Code”, and potentially many other bytecode formats including those for CLISP, Smalltalk, and Parrot). Again, comparison files may be generated based on the data, or other examination techniques may be used.

These techniques may be particularly applicable to identifying encryption algorithms that have been designed with specific data constants.

Collection Information

In one embodiment, files are associated with collections. These collections may be files associated with a particular project, program, subsystem, book, or other group. The association of files with projects may be used to determine which of a number of matching files is the best match.

For example, if a portion of a first file matches similar-sized portions of multiple files within a collection (e.g. within the same project), the indication of similarity may initially only specify one of the files. This simplifies reporting for the user, but without much additional risk from being underinclusive because the details about the collection (e.g., license, vendor, etc.) are likely to be the same for the content files in the collection. For example, collections may be organized in the comparison file library so that this is the case.

(It should be understood that if any of the matches were a superset of the others, that one would be the best match.)

In another example, if a region in a comparison file matches regions in several different examined files, and the similar regions are all (approximately or exactly) the same size, one of the regions may be selected, for example using the techniques described here (e.g., based on other matches to other regions and so on), and the other similar regions not initially indicated. For example, if there is a different region in the same comparison file that is a superset of other matches, it may be that other portions in the same file are the best match, too, and may be indicated to the user as such. This should serve to identify the match that is the most representative within a collection.

As another example, if one file has multiple regions that match with multiple regions from the same collection (as well as individual regions in files from other collections), it may be that the similar regions in the examined file are more likely to be from the collection in which there are multiple region matches, and so the files from the same collection are the best match.

In another embodiment, in which files are associated with collections, a match in a file is considered to be the best match if there are other portions in the same or related examined files that match with file(s) from the same collection. In this way, the similarity of portions of examined files to a collection of files is considered. This would be a useful case if multiple portions of content files were copied from the same source.

Directory Matching

In another embodiment in which files are associated with collections, directory components may be compared to determine whether there are similarities. For example, if there are a number of files that have file and directory names that match with a particular collection, it may be determined that the files match with that collection.

Time Information

In one embodiment, when a portion of an examined file matches with similar-sized portions of multiple examined files, and the techniques above do not result in a selection of the best match, other information associated with the matched comparison files may be used. For example, in one embodiment, the date/time applicable to the comparison files (or the portions of the comparison files) are considered. An assumption may be made that the comparison file(s) with the earliest date/time are the original source of the content. For example, if one comparison file has an associated date of Jan. 10, 2005, and a second comparison file has an associated date of Jan. 20, 2000, the best match is the second comparison file, because it is more likely to be the original. This technique may be particularly relevant when the matching portions are entire files. In such case, the earlier file is most likely to be the original source, and as such, the best match.

Author Information

In one embodiment, information regarding an author may be used. For example, an author may have a particular cryptographic expertise. The inclusion of a particular author's name may be indicative of a particular code match and/or a particular type of encryption. The indication of the author may be determined in code comments at the top or in the code, or in metadata describing the code, such as information from a build tool, source control/content management information, and so on.

Version Control Information

In some embodiments, information from source code control/version management/content management information may be used. For example, metadata in such a management system may indicate what algorithms are included in a content file. The information in the content management system may indicate who added the file, or contents to the file, and what the purpose of adding the content. Other information in the content management system also may be useful.

Standards Information

In some embodiments, reference to a particular standard may be indicative of a particular type of encryption. For example, Internet Engineering Task Force RFC 1321 is entitled “The MD5 Message-Digest Algorithm” by R. Rivest, April 1992. Reference to RFC 1321 may be indicative of the MD5 message digest algorithm. Likewise, reference to particular IEEE standards, ISO standards, or other standards may be useful in identifying an algorithm.

Build File/Compiler Information

In some embodiments, build file information and/or compiler information will indicate files that are included or linked. This information may be used to identify particular libraries. For example, symbols and/or symbol tables may provide information about code that will be used by a particular code file. Likewise, indications about files that need to be built if other files are changed are indicative of dependencies.

Information Aggregation

In some embodiments, an aggregation of certain words or text strings, or other information as described here, may be indicating of a particular algorithm. For example, while one or two words may not themselves be indicative, a collection of words may be indicative of a particular algorithm. Likewise, certain compiler information in combination with certain text may be indicative of an algorithm.

Mathematical Operations Used

Use of certain mathematical operations may be indicative of an encryption algorithm. For example, certain algorithms make use of XOR operations, and large integer math libraries. Although there are many other types of algorithms that use such operations, the use of such operations may be indicative of a match, particularly in combination with other types of matches.

Code Structure

Certain types of programming patterns may be indicative of an encryption algorithm. For example, such algorithms tend to include repetitive computational loops. Although there are many other types of algorithms that have such structure, the presence of such structure may be indicative of a match, particularly in combination with other types of matches.

License Information

In some embodiments, other information associated with the matched files may be used to identify the best match. For example, the licensing information applicable to the comparison files may be considered.

Referring now to FIG. 20, in one embodiment, a method 2000 for examining a software program to identify an algorithm is used. This method may be part, for example, of the method of FIG. 1, and may be used as part of the identifying step (STEP 12). Likewise, the method may be implemented in the identification subsystem of FIG. 2, so as to automatically identify algorithms without user intervention. This method may also be used in other contexts when it is useful to identify a particular algorithm.

The method includes identifying a first portion of the software program that is similar to a portion of a comparison program 2001. The first portion may be any portion of a software program, and may include similarity of computer code, interfaces, character strings, static data, and/or a subroutine call. Zero, one or more of these may be used in combination to identify an algorithm used by a program.

The method also includes determining that the first portion is associated with an algorithm 2002. For example, if the algorithm is known to be implemented in a particular comparison content file, a match between the computer code of the content file and a comparison content file as described above may be indicative of the algorithm being used. If the interface to a known algorithm is used in a content file, this may be indicative of the algorithm being used. Likewise, if constants associated with the algorithm, and computer code associated with the algorithm are both identified, this may be indicative that the first portion is associated with the algorithm.

In some embodiments, two, three, or more portions may be used, and the method may include matching different portions of the comparison program, and making a determination based on whether the different portions indicate the same algorithm.

The method also includes providing an indication that the software program uses the identified algorithm 2003. This may be a notification, screen display warning signal, message (e.g., instant message, electronic mail message, text message). In some embodiments, the indication may include export information and/or documentation as described above. The indication also may include a message or communication to a determination subsystem, as shown in FIG. 2.

In various embodiments, the algorithm may be an encryption algorithm, and the method may include identifying implementation characteristics of the algorithm, such as key length, encryption mode, media on which encrypted data would be stored/communicated, the extent to which the algorithm is accessible to an end user, and so on.

In various embodiments, there may already be export-related information that is available for certain software and hardware components of a system. The system may automatically (e.g., through an outside service, web access, or otherwise) identify the available export information that is available for those components, and include such information in an analysis.

It should be understood generally that the systems and methods described here are exemplary, and that other variations within the spirit and scope of the invention are included. 

1. A method for export compliance, comprising: performing a computer-assisted examination of one or more content files; in response to the examination results, identifying content used by or included in the one or more content files that is indicative of content subject to export control; determining, in response to the identified content, export requirements applicable to the one or more content files; and providing an indication of the determined export requirements.
 2. The method of claim 1, further comprising: receiving information regarding the expected use of the content file; and wherein the determining step further comprises determining in response to the identified content and the received information regarding the expected use.
 3. The method of claim 1 wherein the content is computer software.
 4. The method of claim 3 wherein the content subject to export control is an encryption algorithm.
 5. The method of claim 1, further comprising, identifying content subject to export control by presenting examination results to a user.
 6. The method of claim 1 further comprising aggregating the determined export requirements with export requirements applicable to other content files.
 7. The method of claim 1 further comprising aggregating the determined export requirements with export requirements obtained from a publicly available database of export information.
 8. A system for export compliance, comprising: an examination subsystem for performing an examination of one or more content files; an identification subsystem for identifying in response to examination results content used by or included in the one or more content files that is indicative of content subject to export control; a determination subsystem for determining in response to the identified content, export requirements applicable to the one or more content files; and an indication subsystem, for providing an indication of the determined export requirements.
 9. The system of claim 8, further comprising a receiving subsystem for receiving information regarding the expected use of the content file; and wherein the determining subsystem determines export requirements in response to the identified content and received information regarding the expected use.
 10. The system of claim 9 wherein the content is computer software.
 11. The system of claim 10 wherein the content subject to export control is an encryption algorithm.
 12. The system of claim 9, wherein the identification subsystem identifies content subject to export control by presenting examination results to a user, and receiving user input regarding the content.
 13. A method for export compliance, comprising: examining a software program; identifying a portion of the software program indicative of encryption technology included in or used by the software program; determining export requirements associated with the encryption technology indicated by the identified portion of the software program; and providing an indication of the determined export requirements for the software program.
 14. The method of claim 13, further comprising: receiving information regarding the expected use of the software program; and wherein the determining step further comprises determining export requirements in response to the identified portion of the software program and the received information regarding the expected use.
 15. The method of claim 13 wherein the identified portion is an encryption algorithm.
 16. (canceled)
 17. (canceled)
 18. The method of claim 13, further comprising, identifying a portion of the software program without user intervention.
 19. A system for export compliance, comprising: an examination subsystem for examining a software program; an identification subsystem for identifying a portion of the software program indicative of encryption technology included in or used by the software program; a determination subsystem for determining export requirements associated with the encryption technology indicated by the identified portion of the software program; and an indication subsystem for providing an indication of the determined export requirements for the software program.
 20. The system of claim 19, further comprising a receiving subsystem for receiving information regarding the expected use of the software program; and wherein the determination subsystem determines export requirements in response to the identified portion of the software program and the received information regarding the expected use.
 21. The system of claim 19 wherein the identified portion is an encryption algorithm.
 22. The system of claim 19 wherein the identified portion interfaces with an encryption algorithm.
 23. The system of claim 19 wherein the identification subsystem identifies a portion of the software program by presenting examination results to a user.
 24. The system of claim 19, wherein the identification subsystem identifies a portion of the software program without user intervention. 25-36. (canceled) 